home *** CD-ROM | disk | FTP | other *** search
/ kermit.columbia.edu / kermit.columbia.edu.tar / kermit.columbia.edu / newsgroups / misc.19980424-19980901 / 000226_news@newsmaster….columbia.edu _Tue Jun 23 16:24:09 1998.msg < prev    next >
Internet Message Format  |  1998-08-31  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id QAA18511
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Tue, 23 Jun 1998 16:24:08 -0400 (EDT)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id QAA21154
  7.     for kermit.misc@watsun; Tue, 23 Jun 1998 16:24:08 -0400 (EDT)
  8. Path: news.columbia.edu!news.new-york.net!nntprelay.mathworks.com!peerfeed.ncal.verio.net!bug.rahul.net!rahul.net!a2i!samba.rahul.net!rahul.net!a2i!dold.a2i!dold
  9. From: dold@94.usenet.us.com
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: MSkermit and NVT
  12. Date: 23 Jun 1998 18:13:59 GMT
  13. Organization: a2i network
  14. Lines: 20
  15. Message-ID: <6mor98$h70$1@samba.rahul.net>
  16. References: <6mllfu$skt@glas.apc.org> <6mlpie$ggb$1@apakabar.cc.columbia.edu> <6mm65n$lk$1@samba.rahul.net> <X$2lbT$6Wxkf@cc.usu.edu>
  17. Reply-To: dold@network.rahul.net
  18. NNTP-Posting-Host: waltz.rahul.net
  19. NNTP-Posting-User: dold
  20. X-Newsreader: TIN [version 1.2 PL2]
  21. X-Comment: Encoded From: line allows replies that preserve original subject
  22. Xref: news.columbia.edu comp.protocols.kermit.misc:8913
  23.  
  24. Joe Doupnik (jrd@cc.usu.edu) wrote:
  25.  
  26. :     At one time I considered adding support to MS-DOS Kermit for NVT.
  27. : I read the specs carefully (under NDA) and decided the protocol was not
  28. : suitable for production use, and hence I declined to add the necessary code
  29. : to MSK. TCP/IP is much superior in this instance.
  30.  
  31. I would agree with that, as a former user of NVT.  Junk.  
  32. Poorly written, poorly documented, proprietary at both ends of the link,
  33. with no obvious source for the "other" end of the link, if it's not
  34. included by a unix vendor as part of their release.
  35. Hangs, disconnects, mysterious hotkeys that invoke features that obviously
  36. never worked...
  37.  
  38. Let's see, what can I say nice about it?
  39.  
  40. -- 
  41. ---
  42. Clarence A Dold - dold@network.rahul.net
  43.                 - Pope Valley & Napa CA.